Add support for building for Windows ARM64 devices #3430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Filed as internal issue #USD-10450 ❗ Please make sure that a signed CLA has been submitted! |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CLA sorted - approved by Tim Palmer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change(s)
Add support for Windows ARM64 devices.
This was tested using the following command line:
Python is currently switched off due to lack of support for PySide on these devices. I am looking at that seperately.
I also had to disable imaging, as building boost appears to be broken when using newer CMake versions (similar issue to #3285)
TBB is set to OneTBB, as 2020u3 doesn't support these devices.
I also had to make a small modification in
testWrapper.py, and change line 134 topathPattern = pathPattern + r'(\S*)', as otherwise the escape sequence was invalid.Checklist
[x] I have created this PR based on the dev branch
[x] I have followed the coding conventions
[ ] I have added unit tests that exercise this functionality (Reference:
testing guidelines)
[x] I have verified that all unit tests pass with the proposed changes
[ ] I have submitted a signed Contributor License Agreement (Reference:
Contributor License Agreement instructions)
The CLA is with my management chain, for now.